#product management.

You are a VP of Product. Write a 1-year product strategy document for [product name] in [market]. Company context: [stage, revenue, team size, key constraints]. Customer insight (your job to unpack this): [1-3 customer quotes or feedback themes]. Market context: [key trends or competitive moves]. Strategy document structure: 1) Where to Play — which customer segments and use cases to focus on (and which to deliberately ignore), 2) How to Win — the differentiated capabilities that will make us the obvious choice, 3) Strategic Bets — the 3 big bets we are making this year and the hypothesis behind each, 4) Product Principles — 5 decision-making rules the team will use when facing trade-offs, 5) Roadmap Themes — (not feature lists) 4 quarterly themes that ladder to the bets, 6) Resource Allocation — rough % split across bets, 7) What Success Looks Like — how we know the strategy worked at year end.

You are a product strategist. Help me prioritize this backlog of features using multiple frameworks to cross-check the decision. Feature list: [list 8-12 features or opportunities]. Step 1: Apply RICE scoring — score each on Reach (users/quarter), Impact (0.25/0.5/1/2/3), Confidence (%), and Effort (person-weeks). Show the RICE score calculation. Step 2: Apply the Impact vs Effort 2x2 matrix — categorize into: Quick Wins, Big Bets, Fill-ins, Thankless Tasks. Step 3: Check against strategic alignment — which features directly advance [your stated product strategy]? Step 4: Apply MoSCoW tagging (Must / Should / Could / Won't) for the next 90 days. Step 5: Final recommendation — your top 5 priorities and the order you'd tackle them, with 2-sentence rationale for each. Flag where your scores are most uncertain.

You are a Principal Product Manager. Write a comprehensive PRD for the following feature: [feature name and 1-sentence description]. This feature will be built by a [X-person] engineering team in [timeframe]. PRD sections: 1) Problem Statement — what user pain are we solving and what evidence do we have that this pain is real and significant?, 2) Goals & Success Metrics — 1 primary metric, 2 secondary metrics, 1 guardrail metric (what we must NOT make worse), 3) User Stories — in 'As a [user], I want [action], so that [outcome]' format, 3-5 stories covering the core use case and key edge cases, 4) Functional Requirements — precise, testable spec language (use 'shall/shall not'), 5) Non-Functional Requirements — performance, security, accessibility, 6) Out of Scope — explicitly state what this phase does NOT include, 7) Open Questions — unresolved decisions and who needs to answer them, 8) Launch Criteria (definition of done). User context: [key users and their context].